@omergk28 looking mostly good; here are my comments:

1. Canonical bodies introduce seven dangling slash-command references in the pre-existing ten

specs/opencode-skill-parity.md:66 · behavior · in diff

The closure claim here is scoped to the planning arc, and it holds — verified
the five arc skills reference only enrolled skills. But replacing the terse
bodies breaks closure for four of the pre-existing ten: synced ctx-wrap-up
now instructs the agent to offer /ctx-commit, use /ctx-reflect, run
/ctx-digest next session, and defer to /ctx-journal-enrich-all;
ctx-remember points at /ctx-history and /ctx-digest; ctx-handover and
ctx-kb-note route capture to /ctx-learning-add and /ctx-convention-add.
None of these seven commands exist in the OpenCode tree, and the old
hand-written bodies at ce5a8328 referenced only enrolled skills — so this is
PR-introduced, and they are instruction-level references, not passing mentions.

Cheapest meaningful fix: enroll ctx-learning-add + ctx-convention-add — the
capture-pair rationale that got ctx-task-add/ctx-decision-add in applies
verbatim, since wrap-up's core ceremony is capturing learnings and conventions.
For the rest (commit/reflect/digest/history/journal-enrich-all),
either enroll deliberately or record the dangling references as an accepted gap
in this Decisions section so the next audit doesn't rediscover it.

2. Parity test mirrors the transform's over-reach, so it can't catch it

internal/assets/read/skill/parity_test.go:88 · test-coverage · in diff

sed '/^allowed-tools:/d' deletes every column-0 allowed-tools: line
anywhere in the file, not just the frontmatter key — and stripAllowedTools
intentionally replicates that. Consequence: if a canonical skill body ever
gains a column-0 allowed-tools: line (most plausibly a fenced frontmatter
example in a skill about writing skills), the sync scripts will corrupt the
deployed body and this test will still pass, because expected and actual are
computed by the same over-reaching transform.

Today the tree is safe — every allowed-tools: occurrence sits at frontmatter
line 4, and the one body mention (ctx-skill-create SKILL.md:71) is a table
cell, not column 0 — but this is precisely the class of drift nobody re-checks
by hand. A cheap guard inside this test — assert the canonical source contains
at most one allowed-tools: line and that it sits inside the leading ---
block, and fail loudly otherwise — converts the silent corruption into a red
test without touching either sync script.

Nit

3. Gate restore can leave an untracked generated SKILL.md behind

Makefile:421 · robustness · in diff

If a skill directory is committed without a SKILL.md yet (enrollment done
halfway), the failing gate's restore path copies before/* back over but
cannot delete the SKILL.md the sync just created, leaving untracked residue
in a target that promises to restore state. diff -rq still fails correctly,
and the Copilot gate (line 406) has the identical shape — so this is
consistency-preserving as written. If you tighten it, tighten both siblings
together; don't let them diverge over this.

Thanks for the review @josealekhine — addressed in f3adbc8:

1. Dangling references: enrolled ctx-learning-add + ctx-convention-add as suggested (capture-pair rationale). The remaining five (/ctx-commit, /ctx-reflect, /ctx-digest, /ctx-history, /ctx-journal-enrich-all) are recorded as an accepted gap in the spec's Decisions section — accepted because a follow-up branch (feat/opencode-mirror-sync, ready on my fork, PR opens once this merges) adopts the Codex full-mirror sync model and ships the entire canonical tree, closing all seven references structurally rather than piecemeal.

2. Transform over-reach: added TestAllowedToolsConfinedToFrontmatter exactly as you sketched — at most one allowed-tools: line per canonical skill, and it must sit inside the leading --- block. Red test the moment a body gains one.

3. Gate restore residue: left as-is per your consistency note. The mirror-sync follow-up moves the OpenCode gate to the Codex-style full-replace restore (mirror semantics require it, since sync adds/removes directories); Copilot keeps the sibling shape with its presence model.

One rider: the regenerated search.json now indexes docs/home/codex.md (on main since #163, which landed without its generated site page), so site/home/codex/index.html ships in this commit — an index entry without its page would put dead codex results in site search.

Landed.